Skip to main content

Commonly Used Network Ports in DevOps and Cloud Environments

Here's a breakdown of commonly used network ports and their significance in a DevOps and cloud environment:

Service Port Description
HTTP 80 Used for unencrypted web traffic. It’s the foundation of data communication on the web.
HTTPS 443 Secures HTTP traffic with encryption using SSL/TLS. Essential for secure web browsing.
SSH 22 Enables secure remote login and command execution on servers. Vital for server administration.
FTP 21 Used for file transfers over a network. Commonly seen in legacy systems.
DNS 53 Resolves domain names to IP addresses, enabling human-friendly URLs.
MySQL 3306 The default port for MySQL database. Allows apps to connect and query the database.
Kubernetes API Server 6443 Used for controlling and managing Kubernetes clusters.
Docker Daemon API 2375/
2376		 Interacts with the Docker Engine for container management.
MongoDB 27017 Default port for MongoDB, a popular NoSQL database.
NGINX 80/
443		 Acts as a web server or reverse proxy, handling HTTP/HTTPS traffic.
Grafana 3000 Visualizes metrics and logs, often used in conjunction with Prometheus for monitoring.
Prometheus 9090 Collects and stores time-series data for monitoring.
Tomcat 8080 A web server for Java applications, commonly used for hosting Java-based web applications.
Apache Kafka 9092 Used for distributed messaging and data streaming in real-time.
Redis 6379 An in-memory database used for caching and real-time analytics.
RDP 3389 For remote desktop connections, mainly in Windows environments.
Elasticsearch API 9200 Provides search and analytics capabilities for large datasets.
Jenkins 8080 Automates CI/CD processes in software development.
SMTP 25 Used for sending emails between servers, especially in email server communications.

This table provides a concise overview of each port and its associated service, helping DevOps engineers and cloud professionals understand and manage network communication more effectively.

Labels:

Comments

Post a Comment

Popular posts from this blog

A Complete CI/CD Pipeline

Complete CI/CD Pipeline Using GitHub, Jenkins, Maven, SonarQube, Nexus, and Docker A well-designed CI/CD pipeline plays a critical role in modern DevOps practices by automating software delivery, improving code quality, and reducing deployment risks. In this article, I will explain how I build an automated CI/CD pipeline using GitHub, Jenkins, Maven, SonarQube, Nexus Repository, Docker, and Docker Hub. Source Code Management with GitHub The CI/CD workflow begins with storing the application source code in GitHub. Developers regularly push code changes or create pull requests to collaborate on features and bug fixes. Whenever new code is pushed to the repository, GitHub triggers Jenkins automatically through a webhook. This integration helps start the CI/CD pipeline without manual intervention. Code Checkout Stage in Jenkins The first stage of the pipeline is the checkout process. Jenkins connects to the GitHub repository and pulls the latest version of the source code. ...
Post a Comment
Read more

Terraform for AWS: Step-by-Step Infrastructure Automation That Actually Works

How I Use Terraform to Provision and Manage AWS Infrastructure Efficiently Infrastructure as Code (IaC) has become a critical part of modern cloud operations, and Terraform is one of the most popular tools for automating cloud infrastructure deployment. In this article, I'll share how I use Terraform to build and manage AWS resources such as Virtual Private Clouds (VPCs), EC2 instances, Application Load Balancers (ALBs), and Auto Scaling Groups. Building AWS Infrastructure with Terraform My infrastructure deployment process begins by defining all AWS resources as code. This approach ensures consistency, repeatability, and easier management across multiple environments. The first step is creating a secure network architecture using a VPC. Within the VPC, I configure public and private subnets, route tables, internet gateways, and other networking components required for application deployment. Once the networking layer is ready, I deploy EC2 instances inside private su...
Post a Comment
Read more

Master Linux Administration for DevOps: Powerful Commands, Troubleshooting Tips & Best Practices

Linux administration is one of the most important skills for anyone working in DevOps. From application servers and CI/CD platforms to containers and cloud infrastructure, Linux-based systems are widely used in modern technology environments. In my day-to-day DevOps activities, I regularly work with Linux commands to manage files, monitor processes, troubleshoot services, investigate network problems, analyze logs, and resolve production issues. This guide covers essential Linux administration concepts and commands that are useful for DevOps engineers, along with practical examples of how they can be applied during everyday troubleshooting. 1. Understanding Linux File Permissions Linux uses a permission system to control access to files and directories. The three basic permissions are: Read (r) – Allows a user to view the contents of a file or directory. Write (w) – Allows modifications to a file or directory. Execute (x) – Allows a file to be executed or a director...
Post a Comment
Read more